Skip to content

Conversation

@jakelandis
Copy link
Contributor

This commit updates the CrossClusterShardTests introduced with #101656 to account for TransportRequestHandler.
It also introduces reflections to provide stronger, but still imperfect, educated guesses to which actions and requests
should implement the IndicesRequest.RemoteClusterShardRequest interface. The updated test re-enforced that the
interface was correctly applied in #101656, but the new checks also found a couple classes that should also implement
the interface. Those classes have been updated to implement the IndicesRequest.RemoteClusterShardRequest interface.

@jakelandis jakelandis requested a review from gwbrown July 17, 2024 20:52
@jakelandis jakelandis marked this pull request as ready for review July 17, 2024 20:52
@jakelandis jakelandis requested a review from a team as a code owner July 17, 2024 20:52
@elasticsearchmachine elasticsearchmachine added the needs:triage Requires assignment of a team area label label Jul 17, 2024
mark-vieira
mark-vieira previously approved these changes Jul 17, 2024
@jakelandis jakelandis added >non-issue :Security/Security Security issues without another label and removed needs:triage Requires assignment of a team area label labels Jul 17, 2024
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-security (Team:Security)

@elasticsearchmachine elasticsearchmachine added the Team:Security Meta label for security team label Jul 17, 2024
@jakelandis
Copy link
Contributor Author

@elasticsearchmachine update branch

@jakelandis jakelandis dismissed mark-vieira’s stale review July 22, 2024 16:37

needs a bit more work

@jakelandis jakelandis marked this pull request as draft July 22, 2024 16:39
@jakelandis jakelandis closed this May 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

>non-issue :Security/Security Security issues without another label Team:Security Meta label for security team v9.1.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants